Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ERROR_GEN_FAILURE [code 0x0000001f] error while adding VCSA to AD Domain (77531)

Last Updated: 4/20/2023Categories: TroubleshootingTotal Views: 24690Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Adding vCenter Server Appliance (VCSA) to Active Directory (AD) domain using the command-line interface (CLI) fails.
The error reported is Error: ERROR_GEN_FAILURE [code 0x0000001f].
Server Message Block protocol version 2 (SMB2) is enabled on both the vCenter as well as the in the Domain Controllers (DCs).

Cause

VCSA is not able to communicate to DCs using Port 445.

Resolution

This is not a VMware issue. This issue may occur when port 445 is blocked on an external firewall or other device in the path from the vCenter to the Domain Controllers.

To resolve the issue, make sure to have Port 445 enabled on external firewall if any.

To test if Port 445 is accessible, run the following command
openssl s_client -connect mydomain.com:445

If result is a "CONNECTED" message: port 445 is enabled.
If result is a "errno" or "error" message: port 445 is not enabled.

Related Information

Enabling vCenter Server Appliance to use SMB2

Domain join operation for vCenter Server appliance fails with the Error: ERROR_ACCESS_DENIED when SMBv3 is enabled on Domain Controller

"/opt/likewise/bin/domainjoin-cli", CLI to handle Active Directory Domain Operations Join/Leave/Query on vCenter Server Appliance 6.x

Third-party links:

How to configure a firewall for Active Directory domains and trusts

How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows

Disclaimer: VMware is not responsible for the reilability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
ホストをクラスタに移動するときに、「信頼できるインフラストラクチャ ホストの未構成アラーム」というアラームが発生する (77234)

KB
•
T0 逻辑路由器停止接收来自 T1 逻辑路由器的路由 (77060)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

VMware vCenter Server 8.0.x

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant